Managing content item collections

ABSTRACT

The present disclosure generally relates to managing content item collections. A collection management system receives a request for collection item metadata associated with a collection item. Collection management system obtains a content item identifier corresponding to the collection item identifier. Collection management system requests content item metadata from a content management system. Collection management system receives from the content management system content item metadata corresponding to the content item identifier. Collection management system filters the content item metadata to remove a portion of the content item metadata comprising privileged information. Collection management system retrieves collection item metadata using the collection item identifier. Collection management system adds the filtered content item metadata to the collection item metadata. Collection management system sends to the client device the collection item metadata for the content item to be displayed, without sending the portion of the metadata comprising privileged information.

CROSS-REFERENCE TO RELATED APPLICATIONS

This application is a continuation-in-part of U.S. application Ser. No.15/721,158, filed Sep. 29, 2017, now U.S. Pat. No. 10,592,595, issuedMar. 17, 2020, which claims priority to U.S. Application Ser. No.62/573,099, filed Oct. 16, 2017, which are hereby incorporated byreference in their entireties.

BACKGROUND

Generating high quality interactive media presentations that have apolished look can be difficult. A mechanism for managing content andpresenting the content in an organized and aesthetically pleasing waywithout exposing unfinished work product (e.g., comments, edits, othermetadata, etc.) is needed.

SUMMARY

Additional features and advantages of the disclosure will be set forthin the description which follows, and in part will be apparent from thedescription, or can be learned by practice of the herein disclosedprinciples. The features and advantages of the disclosure can berealized and obtained by means of the instruments and combinationsparticularly pointed out in the appended claims. These and otherfeatures of the disclosure will become more fully apparent from thefollowing description and appended claims, or can be learned by thepractice of the principles set forth herein.

Disclosed are systems, methods, and non-transitory computer-readablestorage media for managing content item collections. For example, in anembodiment, a collection management system receives, from a clientdevice, a request for collection item metadata associated with acollection item. The request includes a collection item identifier. Thecollection management system obtains a content item identifiercorresponding to the collection item identifier. The collectionmanagement system requests content item metadata from a contentmanagement system. The content item metadata corresponds to the contentitem identifier of a content item stored by the content managementsystem. The collection management system receives from the contentmanagement system content item metadata corresponding to the contentitem identifier. The collection management system filters the contentitem metadata to remove a portion of the content item metadatacomprising privileged information. The collection management systemretrieves collection item metadata using the collection item identifier.The collection management system adds the filtered content item metadatato the collection item metadata. The collection management system sendsto the client device the collection item metadata for the content itemto be displayed to a user of the client device, without sending theportion of the metadata comprising privileged information.

In another embodiment, a computing system is disclosed herein. Thecomputing system includes a collections server and one or moreprocessors. The collections server configured to manage one or morecollections of content items. The one or more processors are coupled tothe collections server. The one or more processors are configured toreceive, from a client device, a request for collection item metadataassociated with a collection item. The request includes a collectionitem identifier. The one or more processors are configured to obtain acontent item identifier corresponding to the collection item identifier.The one or more processors are configured to request content itemmetadata from a content management system. The content item metadatacorresponds to the content item identifier of a content item stored bythe content management system. The one or more processors are configuredto receive content item metadata corresponding to the content itemidentifier. The one or more processors are configured to filter thecontent item metadata to remove a portion of the content item metadatacomprising privileged information. The one or more processors areconfigured to retrieve collection item metadata using the collectionitem identifier. The one or more processors are configured to add thefiltered content item metadata to the collection item metadata. The oneor more processors are configured to send to the client device thecollection item metadata for the content item to be displayed to a userof the client device, without sending the portion of the metadatacomprising privileged information.

In another embodiment, a non-transitory computer readable medium isdisclosed herein. The non-transitory computer readable medium includesone or more sequences of instructions that, when executed by one or moreprocessors, causes the one or more processors to perform operations. Theoperations include requesting content item metadata from a contentmanagement system in response to receiving a request for collection itemmetadata. The content item metadata corresponding to a content itemassociated with a collection item identifier. The operations includereceiving content item metadata corresponding to the content item. Theoperations include filtering the content item metadata to remove aportion of the content item metadata comprising privileged information.The operations include retrieving collection item metadata using thecollection item identifier. The operations include adding the filteredcontent item metadata to the collection item metadata. The operationsinclude sending the collection item metadata for the content item to bedisplayed to a user of the client device, without sending the portion ofthe metadata comprising privileged information.

BRIEF DESCRIPTION OF THE DRAWINGS

The above-recited and other advantages and features of the disclosurewill become apparent by reference to specific embodiments thereof whichare illustrated in the appended drawings. Understanding that thesedrawings depict only example embodiments of the disclosure and are nottherefore to be considered to be limiting of its scope, the principlesherein are described and explained with additional specificity anddetail through the use of the accompanying drawings in which:

FIG. 1A shows an example configuration of devices and a network inaccordance with some embodiments;

FIG. 1B shows a block diagram of an example system for managingcollaborative content items;

FIG. 2 shows a block diagram of an example system for managing contentitem collections;

FIG. 3 illustrates an example graphical user interface for viewingcollections associated with a user of a content management system;

FIG. 4 illustrates an example graphical user interface for addingcontent to a new collection;

FIG. 5 illustrates an example graphical user interface for choosingcontent items to add to a collection;

FIG. 6 illustrates an example graphical user interface presenting acollection having embedded content items;

FIG. 7 illustrates an example tile graphical user interface;

FIG. 8 illustrates an example graphical user interface for presenting afull preview of a content item without caption or comments;

FIG. 9 illustrates an example graphical user interface for presenting afull preview of a content item having a caption and/or comments;

FIG. 10 illustrates an example graphical user interface for presentingcollection item metadata in a collection view;

FIG. 11A shows a flow diagram of an example process for creating acollection;

FIG. 11B shows a flow diagram of an example process for adding a contentitem to a collection;

FIG. 12 shows a flow diagram of an example process for presenting acollection;

FIG. 13 shows a flow diagram of an example process for presenting acollection item preview;

FIG. 14 shows a flow diagram of an example process for presentingcollection item metadata;

FIG. 15A shows an example possible system embodiment for implementingvarious embodiments of the present technology; and

FIG. 15B shows an example possible system embodiment for implementingvarious embodiments of the present technology.

DETAILED DESCRIPTION

Various embodiments of the disclosure are discussed in detail below.While specific implementations are discussed, it should be understoodthat this is done for illustration purposes only. A person skilled inthe relevant art will recognize that other components and configurationsmay be used without parting from the spirit and scope of the disclosure.

Additional and/or alternative details and/or implementations of thetechnology disclosed herein can be found in U.S. patent application Ser.No. 15/721,158, titled “MAINTAINING MULTIPLE VERSIONS OF A COLLECTION OFCONTENT ITEMS,” which is hereby incorporated by reference in itsentirety.

The disclosed technology addresses the need in the art for presenting acollection of content items while preventing end users from directlyaccessing the content items and/or content item metadata.

With respect to implementing various embodiments of the disclosedtechnology, an example system configuration 100 is shown in FIG. 1A,wherein electronic devices communicate via a network for purposes ofexchanging content and other data. The system can be configured for useon a wide area network such as that illustrated in FIG. 1A. However, thepresent principles are applicable to a wide variety of networkconfigurations that facilitate the intercommunication of electronicdevices. For example, each of the components of system 100 in FIG. 1Acan be implemented in a localized or distributed fashion in a network.

In system 100, a user (e.g., an individual, group of users, company,etc.) can interact with content management system 106 (e.g., an onlinesynchronized content management system) through client devices 102 ₁,102 ₂, . . . , 102 _(n) (collectively “102”) connected to network 104 bydirect and/or indirect communication. Content management system 106 caninclude a single computing device (e.g., a server) or multiple computingdevices (e.g., multiple servers) that are configured to perform thefunctions and/or operations necessary to provide the services describedherein. Content management system 106 can support connections from avariety of different client devices, such as: desktop computers; mobilecomputers; mobile communications devices, e.g. mobile phones, smartphones, tablets; smart televisions; set-top boxes; and/or any othernetwork enabled computing devices. Client devices 102 can be of varyingtype, capabilities, operating systems, etc. Furthermore, contentmanagement system 106 can concurrently accept connections from andinteract with multiple client devices 102.

A user can interact with content management system 106 via a client-sideapplication installed on client device 102 _(i). In some embodiments,the client-side application can include a content management systemspecific component. For example, the component can be a stand-aloneapplication, one or more application plug-ins, and/or a browserextension. However, the user can also interact with content managementsystem 106 via a third-party application, such as a web browser, thatresides on client device 102 _(i) and is configured to communicate withcontent management system 106. In either case, the client-sideapplication can present a user interface (UI) for the user to interactwith content management system 106. For example, the user can interactwith the content management system 106 via a client-side applicationintegrated with the file system or via a webpage displayed using a webbrowser application.

Content management system 106 can enable a user to store content items,as well as perform a variety of content management tasks, such asretrieve, modify, browse, and/or share the content items. Furthermore,content management system 106 can enable a user to access the contentfrom multiple client devices 102. For example, client device 102 _(i)can upload content to content management system 106 via network 104.Later, the same client device 102 _(i) or some other client device 102_(j) can retrieve the content from content management system 106.

To facilitate the various content management services, a user can createan account with content management system 106. User account database 150can maintain the account information. User account database 150 canstore profile information for registered users. In some cases, the onlypersonal information in the user profile can be a username and/or emailaddress. However, content management system 106 can also be configuredto accept additional user information such as birthday, address, billinginformation, etc.

User account database 150 can include account management information,such as account type, usage information, (e.g., file access or edithistory), storage space used, content storage locations, securitysettings, personal configuration settings, content sharing data, etc.Account management module 124 can be configured to update and/or obtainuser account details in user account database 150. The accountmanagement module 124 can be configured to interact with any number ofother modules in content management system 106.

An account can be used to store content items, such as digital data,documents, collaborative content items, text files, audio files, imagefiles, video files, webpages, executable files, binary files,placeholder files that reference other content items, etc., from one ormore client devices 102 authorized on the account. The content items canalso include collections for grouping content items together withdifferent behaviors, such as folders, playlists, albums, etc. Forexample, an account can include shared collections or group collectionsthat are linked with and available to multiple user accounts. Thepermissions for multiple users may be different for a shared collection.

The content items can be stored in content storage 160. Content storage160 can be a storage device, multiple storage devices, or a server.Alternatively, content storage 160 can be a cloud storage provider ornetwork storage accessible via one or more communications networks.Content management system 106 can hide the complexity and details fromclient devices 102 so that client devices 102 do not need to knowexactly where or how the content items are being stored by contentmanagement system 106. In some embodiments, content management system106 can store the content items in the same collection hierarchy as theyappear on client device 102 _(i). However, content management system 106can store the content items in its own order, arrangement, or hierarchy.Content management system 106 can store the content items in a networkaccessible storage (NAS) device, in a redundant array of independentdisks (RAID), etc. Content storage 160 can store content items using oneor more partition types, such as FAT, FAT32, NTFS, EXT2, EXT3, EXT4,HFS/HFS+, BTRFS, and so forth.

Content storage 160 can also store metadata describing content items,content item types, and the relationship of content items to variousaccounts, collections, or groups. The metadata for a content item can bestored as part of the content item or can be stored separately. In onevariation, each content item stored in content storage 160 can beassigned a system-wide unique identifier.

Content storage 160 can decrease the amount of storage space required byidentifying duplicate content items or duplicate segments of contentitems. Instead of storing multiple copies, content storage 160 can storea single copy and then use a pointer or other mechanism to link theduplicates to the single copy. Similarly, content storage 160 can storecontent items more efficiently, as well as provide the ability to undooperations, by using a content item version control that tracks changesto content items, different versions of content items (includingdiverging version trees), and a change history. The change history caninclude a set of changes that, when applied to the original content itemversion, produce the changed content item version.

Content management system 106 can be configured to support automaticsynchronization of content items from one or more client devices 102.The synchronization can be platform agnostic. That is, the content itemscan be synchronized across multiple client devices 102 of varying type,capabilities, operating systems, etc. For example, client device 102_(i) can include client software, which synchronizes, via asynchronization module 132 at content management system 106, content inclient device 102 _(i)'s file system with the content in an associateduser account. In some cases, the client software can synchronize anychanges to content in a designated collection and its sub-collections,such as new, deleted, modified, copied, or moved content items orcollections. The client software can be a separate software application,can integrate with an existing content management application in theoperating system, or can be some combination thereof. In one example ofclient software that integrates with an existing content managementapplication, a user can manipulate content items directly in a localcollection, while a background process monitors the local collection forchanges and synchronizes those changes to content management system 106.Conversely, the background process can identify content items that havebeen updated at content management system 106 and synchronize thosechanges to the local collection.

A user can view or manipulate content via a web interface generated andserved by user interface module 122. For example, the user can navigatein a web browser to a web address provided by content management system106. Changes or updates to content in the content storage 160 madethrough the web interface, such as making edits to text or media thatare part of the content item, can be propagated to other client devices102 authorized to access the content item. For example, multiple clientdevices 102, each with their own client software, can be associated witha single account and content items in the account can be synchronizedbetween each of the multiple client devices 102.

Content management system 106 can include a communications interface 120for interfacing with various client devices 102, and can interact withother content and/or service providers 109 ₁, 109 ₂, . . . , 109 _(n)(collectively “109”) via an Application Program Interface (API). Certainsoftware applications can access content storage 160 via an API onbehalf of a user. For example, a software package, such as an apprunning on a smartphone or tablet computing device, can programmaticallymake calls directly to content management system 106, when a userprovides credentials, to read, write, create, delete, share, orotherwise manipulate content. Similarly, the API can allow users toaccess all or part of content storage 160 through a web site.

Content management system 106 can also include authenticator module 126,which can verify user credentials, security tokens, API calls, specificclient devices, and so forth, to ensure only authorized clients andusers can access content items. Further, content management system 106can include analytics module 134 module that can track and report onaggregate file operations, user actions, network usage, total storagespace used, as well as other technology, usage, or business metrics. Aprivacy and/or security policy can prevent unauthorized access to userdata stored with content management system 106.

Content management system 106 can include sharing module 130 formanaging sharing content items. Sharing content items can include makingthe content item accessible from any computing device in networkcommunication with content management system 106. Sharing content itemscan also include linking a content item in content storage 160 with twoor more user accounts so that each user account has access to thecontent item. The sharing can be performed in a platform agnosticmanner. That is, the content can be shared across multiple clientdevices 102 of varying type, capabilities, operating systems, etc. Thecontent can also be shared across varying types of user accounts.

In some implementations, to share a content item, sharing module 130 canbe configured to add a user account identifier to the content entryassociated with the content item, thus granting the added user accountaccess to the content item. Sharing module 130 can also be configured toremove user account identifiers from a content entry to restrict a useraccount's access to the content item.

In some implementations, to share a content item, sharing module 130 canbe configured to generate a custom network address, such as a uniformresource locator (URL), which allows web browsers to access the contentin content management system 106, which in some implementations, can beallowed without any authentication. To accomplish this, sharing module130 can be configured to include content identification data in thegenerated URL, which can later be used to properly identify and returnthe requested content item. For example, sharing module 130 can beconfigured to include the user account identifier and the content pathin the generated URL. Upon selection of the URL, the contentidentification data included in the URL can be transmitted to contentmanagement system 106 which can use the received content identificationdata to identify the appropriate content entry and return the contentitem associated with the content entry.

In some implementations, content management system 106 can includecollaborative content item management module 136. Collaborative contentitem management module 136 can provide an interactive content itemcollaboration platform whereby users can simultaneously createcollaborative content items, comment in the collaborative content items,and manage tasks within the collaborative content items. Collaborativecontent item management module 136 can be implemented as a separatesubsystem of content management system 106. For example, in someimplementations, the management of content items, as described above,can be performed by one or more servers of content management system 106specifically configured to manage content items. The management ofcollaborative content items can be performed by one or more servers ofcontent management system 106 that are separate from the content itemmanagement servers and that are specifically configured to managecollaborative content items. In some implementations, the same serverscan be configured to manage both content items and collaborative contentitems. Similarly, content items and collaborative content items can beboth be stored in content storage 160. Alternatively, content storage160 may store content items while collaborative content items can bestored separately in collaborative content item storage 165.

Collaborative content items can be files that users can create and editusing a collaborative content items editor, and can containcollaborative content item elements. Collaborative content items and/orthe data defining collaborative content items can be stored separatelyfrom content items. Collaborative content item elements may include acollaborative content item identifier, one or more author identifiers,collaborative content item text, collaborative content item attributes,interaction information, comments, sharing users, etc. Collaborativecontent item elements can be stored as database entities, which allowsfor searching and retrieving the collaborative content items. Multipleusers may access, view, edit, and collaborate on collaborative contentitems at the same time or at different times. In some embodiments thiscan be managed as multiple users access a content item through a webinterface and there they can work on the same copy of the content itemat the same time.

In some implementations, portions of a collaborative content item can berepresented by a list of attributed text (e.g., a string of text whereeach character or character range has a set of attributes). An attributecan be a (key, value) pair: for example, (“bold”, “true”), (“list”,“bullet1”), or (“author”, authorID). Furthermore, a collaborativecontent item can be stored as a sequence of change sets. A change setrepresents an edit to a particular version of a collaborative contentitem. Applying a change sets can insert and delete characters and applyattributes to ranges. Thus, a given change set can be applied to aparticular collaborative content item representation to generate anothercollaborative content item representation. For example, a collaborativecontent item representation “abc\n” and a change set “insert d atposition 2”, which when applied, would yield a collaborative contentitem representation “abdc\n”. Applying all of the change sets, in agiven order, to an initial version of a collaborative content itemrepresentation, can produce a current version of the collaborativecontent item comprising a list of attributed text representation.Multiple users may access, view, edit, and collaborate on acollaborative content item at the same time or at different times. Insome embodiments this can be managed by providing multiple users withaccess to a content item through a web interface where they can interactwith a same copy of the content item at the same time.

While content management system 106 is presented with specificcomponents, it should be understood by one skilled in the art, that thearchitectural configuration of system 106 is simply one possibleconfiguration and that other configurations with more or fewercomponents are possible.

FIG. 1B shows an example collaborative content item management module136, according to some embodiments. Collaborative content itemmanagement module 136 may include collaborative content item processinginterface module 174, collaborative content item editor module 176, usernotification module 178, and/or collaborative content item presentationmodule 180. One or more of collaborative content item processinginterface module 174, collaborative content item editor module 176, usernotification module 178, and collaborative content item presentationmodule 180 may be coupled to one another or to modules not explicitlyshown.

Collaborative content item processing interface module 174 may beconfigured to interface with collaborative content item managementmodule 136. In various embodiments, collaborative content itemprocessing interface module 174 may provide collaborative content itemsto one or more modules of collaborative content item management module136, as described further herein.

Collaborative content item editor module 176 may be configured to createand/or modify collaborative content items. A collaborative content itemmay be created in a variety of ways. In some embodiments, collaborativecontent item editor module 176 enables creation of the collaborativecontent item into the content management system 106. Collaborativecontent item editor module 176 may enable access to or be anycollaborative content item editing application (e.g., Microsoft Word®,Google Docs®, or the like) either in the cloud or executed locally. Inone example, content management system 106 may provide to one of clientdevices 120 a user interface element (e.g., a box or a button) thatallows creation of a new collaborative content item.

Once the user requests to create or invoke the collaborative contentitem, collaborative content item editor module 176 may create and/orinvoke a collaborative content item. The collaborative content item maybe subsequently edited, altered, viewed, changed, stored, and/or thelike by an editing application (e.g., either stored locally on a clientdevice 102 or in the cloud). In various embodiments, one or moredifferent client devices 120 may utilize different editing applicationsto make changes to the collaborative content item. Collaborative contentitem editor module 176 and/or other editing applications may allow forthe collaborative content item to be changed by multiple different usersusing different client devices 120 at the same time or substantially atthe same time (e.g., in real time or substantially in real time).

Collaborative content item editor module 176 may receive from usersadditional content for the collaborative content item. For example,collaborative content item editor module 176 may be configured toreceive from the client devices 102 changes or edits to thecollaborative content item. In various embodiments, the changes mayinclude text, characters strings, or the like. The changes may alsoinclude annotations to the collaborative content item, comments to thecollaborative content item, files to be attached to the collaborativecontent item, pictures to be attached to the collaborative content item,links to be attached to the collaborative content item, tasks related tothe collaborative content item, or the like that can be incorporatedinto the collaborative content item. In various embodiments, edits tothe collaborative content item are collaborative. For instance,collaborative content item editor module 176 may obtain edits (e.g.,text changes and/or additions of audio files, pictures, tables, or thelike) from any number of client devices 102 at a given time (or in realtime). Collaborative edits may be incorporated in a variety of formats,including formats that provide different text attributes such as colors,fonts, styles, or the like for different users.

In various embodiments, collaborative content item editor module 176(and or a security or permissions module associated with a server) mayestablish permissions and/or security for the collaborative contentitem. For example, collaborative content item editor module 176 mayenable event attendees to view and/or make edits to the collaborativecontent item while others may not have rights to view the collaborativecontent items and/or make changes. Permissions and/or security may beenforced in any number of ways. However, access to the collaborativecontent item may, in various embodiments, be provided to attendees ofthe event or a subset of attendees.

In various embodiments, access to the collaborative content item islimited based on storage access rights. For example, a user with accessrights to cloud storage may access, view, and/or make changes to thecollaborative content item. In some embodiments, a user with accessrights assigned by the content management system 106 may access, view,and/or make changes to the collaborative content item.

User notification module 178 may be configured to notify users of eachof the client devices 102 of information related to the state and/orcontents of the collaborative content item. Notifications may be sent,for example as an email notification, a chat message notification, anotification in a display of the collaborative content item, or inrelation to the collaborative content item through a file system orother organizational system. In various embodiments, user notificationmodule 178 provides notifications about changes to the client devices102.

Collaborative content item presentation module 180 may provide to theclient devices 102 selected collaborative content items. Thecollaborative content items may be displayed in the client devices 102through a native application, an Internet browsing window, or the likesupported by the client devices 120 . . . .

It will be appreciated that collaborative content item presentationmodule 180 may restrict writing permissions to the collaborative contentitems at any time. In an example, prior to occurrence of the event,collaborative content item presentation module 180 may restrict writingpermissions to the collaborative content item (and turn thecollaborative content item into a read-only collaborative content item)for all users except the creator or invoker of the collaborative contentitem. In some embodiments, the creator or invoker of the collaborativecontent item may select a subset of recipients to receive writingpermissions.

Collaborative content item presentation module 180 may also support acollaborative content item viewing portal users can use to view existingcollaborative content items. The collaborative content item viewingportal may order specific collaborative content items based on one ormore ordering factors. “Ordering factors,” as used herein, may includeany factors used to order collaborative content items. Ordering factorscan include factors used to order collaborative content itemschronologically. More specifically, in some embodiments, thecollaborative content item viewing portal orders collaborative contentitems according to the date(s) and/or times the collaborative contentitems were created. The collaborative content item viewing portal mayalso order collaborative content items according to the date(s) and/ortime(s) the collaborative content items were edited. In variousembodiments, the collaborative content item viewing portal orderscollaborative content items according to the date(s) and/or time(s) ofcorresponding events to which the collaborative content items wererelated. Ordering factors can also include factors used to ordercollaborative content items according to the preferences of a specificuser, such as whether the user has accepted events to which thecollaborative content items were related.

In some embodiments, a collaborative content item viewing portal may bededicated to a particular user who has received access to thecollaborative content item because the particular user was related to anevent. The user's collaborative content item viewing portal may provideaccess to any number of collaborative content items including thecollaborative content item. The collaborative content items representedin the collaborative content item viewing portal may be ordered in anynumber of ways. For example, the collaborative content item viewingportal may order collaborative content items based on date and time ofcorresponding events.

The collaborative content item viewing portal may support searchfunctions. For instance, the collaborative content item viewing portalmay enable or allow searching for collaborative content items accordingto textual strings, titles, event attendees, and/or other attributes.The search functions may allow a specific user to search one or morecollaborative content items for that user or for other users.

FIG. 2 is a block diagram of an example system 200 for managing contentitem collections. For example, system 200 can correspond to system 100of FIG. 1A.

In some implementations, content management system 106 can includecollections module 204. For example, collections module 204 can be astandalone software server. Collections module 204 can be a softwaremodule that is part of a larger software system or server. Collectionsmodule 204 can run on collections server 202 (e.g., a computing device)that can be one of a plurality of servers that correspond to or comprisecontent management system 106.

In some implementations, collections module 204 can manage collectionsof content items. For example, a collection can be a collaborativecontent item, as described above. However, while collaborative contentitems are usually freeform and relatively unrestricted with respect tocontent, layout, structure, and appearance, collections are structuredcollaborative content items that constrain the type of content that canbe added to a collection as well as the a layout of the content withinthe collection. The collection is primarily constructed of embeddedcontent items and content item metadata arranged in a grid of tiles,where each tile includes a single content item and associated metadata.Each tile can include a link to a corresponding content item managed bycontent item server 220. Thus, collections module 204 can workcooperatively with content item server 220 to store and retrieve contentitems referenced by each of the tiles in a collection so that therelevant content items can be embedded into the tiles of a collection.

In some implementations, content management system 106 can includecollections storage 206. For example, collections storage 206 can be arepository of collections configuration data managed by collectionsmodule 204. Thus, collections storage 206 can store configuration datathat defines the layout and content for many different collections.

In some implementations, collections storage 206 can include collectionsdata 208. For example, collections data 208 can be a table or other datastructure that stores a mapping of collection identifiers and attributedata for each collection stored in collections storage 206. For example,collections data 208 can include for each collection entry a collectionidentifier and attributes for the identified collection. The attributesfor a collection can include attributes that specify header informationfor the collection. For example, the header information can include aheader background image identifier (e.g., a link or URL to an imagerepresenting the collection). The header information can include textcorresponding to the title for the collection. The header informationcan include a logo or other image (e.g., a link or URL to the logoimage) that represents a company, entity, user, product, or groupassociated with the collection.

In some implementations, a collection entry in collections data 208 caninclude text corresponding to an introductory statement for thecollection. For example, the introductory text can be provided by a userresponsible for creating or editing the collection. The introductorytext can provide an overall description or introduction to the contentincluded in the corresponding collection.

In some implementations, collection storage 206 can include collectionitems 210. For example, collections items 210 can be a table or otherdata structure that includes entries corresponding to tiles in acollection. Each entry or record in collections items 210 can correspondto a single tile. Each entry can include data the define the attributesfor each tile. For example, a tile entry can include a collectionidentifier corresponding to the collection in which the tile and/orcorresponding content item is embedded. The tile entry can include acollection item identifier that uniquely identifies the tile across allcollections managed by collections module 204. The collection itemidentifier can be used by collections module 204 to determine the orderof tiles when presenting a collection. For example, collections module204 can arrange tiles and/or corresponding content items within acollection according to an order determined based on the collection itemidentifier. A tile with a collection item identifier of one, forexample, can be presented in a top row at the left most position withina collection. A tile with a collection identifier of two can bepresented in the top row at a middle position within the collection.Collections module 204 can continue rendering the collection display(e.g., graphical user interface, web page, etc.) by row by row, top tobottom and left to right until each tile and/or corresponding contentitem is embedded into the collection display.

The tile entry can include an identifier that identifies the contentitem embedded in or linked to the corresponding tile. The content itemidentifier can be, for example, a uniform resource locator (URL) thatcan be used to obtain metadata for the content item from content itemserver 220. For example, when embedding content item metadata into atile of a collection, collections module 204 can insert a URL thatincludes the corresponding collection item identifier for the tile. Whena client (e.g., CMS client 250) needs to obtain metadata for the contentitem embedded in the tile, the client can use the URL to request themetadata for the tile from collections module 204. Collections module204 can then use the collection item identifier to content itemidentifier mapping in collection items 210 to obtain the content itemidentifier (e.g., URL) corresponding to the collection item identifier.Collections module 204 can then request the metadata for thecorresponding content item from content item module 226 on content itemserver 220 using the content item identifier. For example, content itemmodule 226 provides content item management and represents one or moreof the modules 120, 122, 124, 126, 130, 132 and/or 124 described abovewith reference to FIG. 1A. Collections module 204 can then filter thecontent item metadata to remove certain metadata (e.g., content itemcomments) that should not be presented by the client and send thefiltered metadata to the client for presentation to the user. Thus, byavoiding sending the content item identifier to the client, collectionsmodule 204 can prevent the client from directly accessing the contentitem metadata stored in content storage 160 and can restrict theclient's access to content item metadata.

The tile entry can include a protected shared link (PSL) that can beused by a client to obtain the content item (e.g., an image representingthe content item) corresponding to the tile entry from content itemserver 220. For example, a protected shared link can be an encryptedpayload of data that can be used by a client (e.g., CMS client 250) toobtain a content item (e.g., content item image) without allowing theclient direct access to the content item identifier and/or the contentitem stored in content storage 160. For example, the payload can includean identifier (e.g., URL) for the content item (e.g., content item 222)stored in content storage 160. The payload can include a collectionidentifier. The payload can include a creation time and a time to liveduration. For example, the creation time and time to live duration canbe used to specify a window of time during which the corresponding PSLis valid. Collections module 204 can encrypt the payload using a sharedsecret shared by collections module 204 and content item module 226.Collections module 204 can then generate a link (e.g., URL) thatincludes the encrypted payload and embed the link in the correspondingtile in a collection. By encrypting the content item identifier,collections module 204 can prevent the client from directly accessingthe corresponding content item through content item module 226.

When the client needs to obtain the content item from content itemmodule 226, the client can send the encrypted payload to content itemmodule 226. Content item module 226 can then validated the encryptedpayload by decrypting the payload using the shared secret and confirmingthat the current time is within the time window specified in thepayload. After validating the payload, content item module 226 can usethe content item identifier in the payload to obtain the identifiedcontent item from content storage 160. Content item module 226 cangenerate an image (e.g., a tile image, thumbnail image, full previewimage, etc.) corresponding to the content item and send the content itemimage to the client. The client can then present the content item imagein the corresponding tile of the collection.

The tile entry can include comment thread identifiers and/or commentidentifiers that can be used to identify and/or obtain collectioncomments from comments 212. For example, content management system 106can maintain content item comments (e.g., comments 224) and collectioncomments (e.g., comments 212) separately. When accessing a content itemdirectly through content module 226 and/or content storage 160, a clientmay have access to the content item comments 224 managed by content itemmodule 226. However, when accessing a content item through a collectionmanaged by collections module 204, a client is restricted to accessingonly the comments 212 associated with the collection and/or tiles withina collection. This restriction is enforced by preventing the client fromreceiving or otherwise directly accessing the content item identifier,as described above. Thus, a tile entry can include comment threadidentifiers and/or comment identifiers that identify comments and/orcomment threads stored in comments 212 in collections storage 206. Thetile entry can include a caption attribute that stores text describingthe corresponding tile and/or content item.

In some implementations, a tile entry can include layout informationthat describes how a tile should be presented in a collection. Forexample, the layout information can specify that a tile should bepresented in a narrow presentation or a full width presentation. Forexample, the narrow presentation can present tiles in a smaller formatthat the full width presentation. The full width presentation canpresent tiles that span the full width of the collections graphical userinterface, as described further below. The layout information canspecify the orientation of tile metadata with respect to the tile and/orembedded content item. For example, the metadata orientation can specifythat metadata (e.g., title, content item identifier, modified date,comments, and/or other graphical elements should be presented below, tothe left, or to the right of the content item embedded in thecorresponding tile, as described further below. The layout informationcan specify a portion of a content item to be presented in a tile. Forexample, a content item may be larger than the display area provided bya tile. A user can provide input to adjust the content item within thetile so that a specific portion of the content item is presented by thetile. Collections module 204 can store information describing thelocation of the specific portion of the content item so that thespecific portion of the content item can be presented when the tile isdisplayed.

In some implementations, content management system can include contentitem server 220. For example, content item server 220 can be one of manyservers that comprise content management system 106. Content item server220 can include content item module 226. As described above, contentitem module 226 can provide content item management and can representone or more of the modules 120, 122, 124, 126, 130, 132 and/or 124described above with reference to FIG. 1A. For example, content itemmodule 226 can manage content item 222 and comments 224 in contentstorage 160.

In some implementations, system 200 can include client device 240. Forexample, client device 240 can correspond to client device 102 _(i)described above with reference to FIG. 1A. Client device 240 can be acomputing device (e.g., hardware and/or software), such as a laptopcomputer, desktop computer, tablet computer, smartphone, wearable deviceor other type of computing device.

In some implementations, client device 240 can include contentmanagement system (CMS) daemon 242. For example, CMS daemon 242 can be abackground software process (e.g., part of the operating system,standalone process, etc.) that manages, in coordination with contentmanagement system 106, synchronization of content items (e.g., contentitem 246) in managed content 244 with content items (e.g., content item222) in content storage 160 managed by content management system 106, asdescribed above.

In some implementations, client device 240 can include contentmanagement system (CMS) client 250. For example, CMS client 250 can be anative application of client device 240. For example, a native softwareapplication can be an application that is built specifically for thehardware and/or software configuration of client device 240. Thus, thegraphical user interfaces (and other functionality) of CMS client 250described below can be implemented using instructions, applicationprogramming interfaces (APIs), and other technologies native to clientdevice 240. To generate the various graphical user interfaces belowand/or implement various features described herein, CMS client 250 canrequest data (e.g., content items, notifications, etc.) from contentmanagement system 106 (e.g., user interface module 122, collaborativecontent item management module 136, collections module 204, etc.) over anetwork connection (e.g., through network 104). Content managementsystem 106 can obtain data from content storage 160, collaborativecontent item storage 165, collections storage 206, and/or other modulesof content management system 106 and send the data to CMS client 250.CMS client 250 can then present the data on various graphical userinterfaces generated by CMS client 250, as described further below.

Alternatively, CMS client 250 can be a web client executed by a webbrowser running on client device 240. Thus, the graphical userinterfaces (and other functionality) of CMS client 250 can beimplemented using instructions, APIs, and other technologies that arenot native to client device 240. For example, CMS client 250 can bebuilt as a web application using non-native web code or instructions(e.g., HTML, JavaScript, etc.). Content management system 106 can serveCMS client 250 to a web browser on client device 240 and the web browsercan execute CMS client 250 to present the graphical user interfaces (andother functionality) to the user, as described in detail below. Togenerate the various graphical user interfaces below and/or implementvarious features described herein, CMS client 250 (e.g., the webbrowser) can request various data views (e.g., graphical userinterfaces, web pages, etc.) from content management system 106. Contentmanagement system 106 can generate the data views (e.g., the graphicaluser interfaces described below) for presenting content managementsystem data (e.g., content items, notifications, comments, tasks, etc.)and send the data views to CMS client 250 over a network connection(e.g., through network 104). For example, content management system 106can obtain data from content storage 160, collaborative content itemstorage 165, collections storage 206, and/or software modules of contentmanagement system 106 (e.g., user interface module 122, collaborativecontent item management module 136, collections module 204, etc.),generate the data views based on the data, and send the data views toCMS client 250.

In some implementations, when a user provides input selecting acollection, CMS client 250 can send the collection identifiercorresponding to the selected collection to collections module 204. Inresponse, collections module 204 can use the collection identifier toobtain the collections data from collections data 208, the collectionitem identifiers from collections items 210, and generate the PSLs foreach tile. Collections module 204 can then send the collections data(e.g., collection header information), collection item identifiers(e.g., tile identifiers), and PSLs to CMS client 250 so that CMS client250 can obtain the relevant content items, metadata, comments, etc., andrender the collection graphical user interface, as illustrated below.

To avoid repeating the description of how content items and/or metadataare embedded into a collection, the reader should understand that anycontent item (e.g., image, text document, multimedia document, slideshowpresentation, video, or other media) added to a collection can beembedded into (e.g., linked into) the collection using protected sharedlinks, as described above. Thus, the header background image, the logo,and all tiles within a collection have corresponding PSLs that providethe mechanism by which CMS client 250 can obtain or retrieve thecorresponding content items from content storage 160. Collection itemmetadata (e.g., tile metadata, content item metadata) presented by acollection is embedded into (e.g., linked into) the collection usingcollection item identifiers, as described above. For example, CMS client250 can obtain collection item metadata by sending the collection itemidentifier to collections module 204. Collection module 204 can use thecollection identifier to content identifier mapping, as described above,to determine the content item identifier needed to retrieve the relevantcontent item metadata for a collection item (e.g., tile). Collectionmodule 204 can obtain collection metadata (e.g., caption, comments,etc.) for a tile using the collection item identifier, as describedabove. Collection module 204 can send the content item metadata and/orthe collection item metadata to CMS client 250. CMS client 250 canpresent the content item metadata and/or the collection item metadata inthe appropriate tile when presenting the collection on a display ofclient device 240.

FIG. 3 illustrates an example graphical user interface 300 for viewingcollections associated with a user of content management system 106. Forexample, GUI 300 can be presented on a display of client device 240 inresponse to a user of client device 240 selecting graphical element 304presented on a graphical user interface that provides a view of a useraccount of content management system 106. For example, a user can loginto the user's account with content management system 106 to cause CMSclient 250 to present a graphical user interface that presents contentitems, folders, collections, and/or other data associated with theuser's account. The graphical user interface can present a graphicalelement 304 in area 302 that when selected causes CMS client 250 topresent collections associated with the user's account.

In some implementations, GUI 300 can present collections associated witha user account. For example, when CMS client 250 receives a selection ofgraphical element 312, CMS client 250 can present information describingcollections created by the user associated with the user account in area310. When CMS client 250 receives a selection of graphical element 314,CMS client 250 can present information describing collections sharedwith the user account in area 310.

In some implementations, GUI 300 can present a collection in collectionarea 316. Collection area 316 can include information describing asingle collection. Multiple collection areas 316 can be presented inarea 310 to describe different collections. Collection area 316 caninclude collection image 318. For example, collection image 318 can bean image selected by a collection creator or editor to represent thecorresponding collection. In some implementations, collection image cancorrespond to the header background image selected for a collection, asdescribed further below. Collection area 316 can include title 320corresponding to the collection. Collection area 316 can includegraphical element 322 indicating the number of items (e.g., contentitems, collection items, tiles, etc.) in the corresponding collection.Collection area 316 can include graphical element 324 indicating whenthe collection was shared with the user and/or other users. Collectionarea 316 can include graphical elements 326 identifying the users ofcontent management system 106 with whom the corresponding collection wasshared. Alternatively, graphical elements 326 can identify the users whohave viewed the collection. Collection area 326 can include graphicalelement 328 indicating the number of times the corresponding collectionhas been viewed by users of content management system 106.

In some implementations, collection area 326 can include graphicalelement 330 for sharing the corresponding collection. For example, whenCMS client 250 receives user input selecting graphical element 330, CMSclient 250 can present a graphical user interface for selecting otherusers with whom the corresponding collection can be shared. The user ofclient device 240 can then select one or more users and CMS client 250can cause collections module 204 to share the collection with theselected users. Collections module 204 can, for example, send a link tothe collection to the other users and/or add the collection to the otherusers' accounts managed by content management system 106.

In some implementations, GUI 300 can include graphical element 340 forcreating a new collection. For example, in response to receiving userinput selecting graphical element 340, CMS client 250 can causecollections module 204 to generate a new collection. Collections module204 can then send the new collection (e.g., an empty collection at thispoint) to CMS client 250. CMS client 250 can then present the emptycollection, as illustrated by FIG. 4.

FIG. 4 illustrates an example graphical user interface 400 for addingcontent to a new collection. For example, GUI 400 can be presented byCMS client 250 on a display of client device 240 in response toreceiving user input selecting graphical element 340 of FIG. 3. CMSclient 250 can receive an empty collection from collections module 204and present the empty collection on GUI 400.

In some implementations, GUI 400 can include collection header area 410.For example, area 410 can include graphical element 412 for adding aheader background image to the collection. For example, in response toreceiving user input selecting graphical element 412, CMS client 250 canpresent a graphical user interface (e.g., similar to GUI 500 below) forselecting an image to represent the new collection. After the user hasselected an image (e.g., a content item from content storage 160, animage from another source, etc.), client device 240 can send the imageand/or content item identifier to collections module 204. Collectionsmodule 204 can then generate a protected shared link (PSL) for theheader background image, as described above, and store the PSL in theheader information for the collection. CMS client 250 can then use thePSL to obtain the corresponding image and present the image in headerarea 410.

In some implementations, header area 410 can include graphical element414 for adding a logo to the collection header information. For example,in response to receiving user input selecting graphical element 414, CMSclient 250 can present a graphical user interface (e.g., similar to GUI500 below) for selecting an image (e.g., a logo) to present on the newcollection. The image can represent a group, company, product, or someother entity, for example. After the user has selected an image (e.g., acontent item from content storage 160, an image from another source,etc.), client device 240 can send the image and/or content itemidentifier to collections module 204. Collections module 204 can thengenerated a protected shared link (PSL) for the logo image, as describedabove, and store the PSL in the header information for the collection.CMS client 250 can then use the PSL to obtain the corresponding logoimage and present the logo image in header area 410.

In some implementations, header area 410 can include graphical element416 for specifying a title for the new collection. For example, a usercan select graphical element 416 and enter text to specify a title forthe new collection. After entering the text, CMS client 250 can send thetext to collections module 204. Collections module 204 can store thetext as the title in the header information for the collection, asdescribed above.

In some implementations, header area 410 can include graphical element418 for adding an introductory description to the new collection. Forexample, a user can select graphical element 418 and enter text tospecify an introductory description for the new collection. Afterentering the text, CMS client 250 can send the text to collectionsmodule 204. Collections module 204 can store the text as theintroduction for the collection in the header information for thecollection, as described above.

In some implementations, GUI 400 can include tile area 430. For example,tile area 430 can include tiles corresponding to the content itemsembedded in the collection. When GUI 400 presents an empty collection,tile area 430 can present empty tiles (e.g., boxes with dashed lines)representing a possible layout of tiles should content items be added tothe collection later. For example, a tile can have a narrow format, suchas tiles 432, 434, and 436. The narrow format of these tiles can allowfor multiple tiles to be arranged in a single horizontal row. A tile canhave a wide format, such as tile 438, that causes the tile to bepresented across the full width (or nearly the full width) of tile area430. Thus, when a tile has a wide format, only one tile will bepresented in a single horizontal row, as illustrated by tile 438.

In some implementations, the position of tiles within tile area 430 canbe predefined. For example, the size of narrow format and wide formattiles can be predefined so that the tiles can be arranged within tilearea 430 according to predefined positions and/or arrangements. Thus, acollection can be created according to a template that constrains thelayout of tiles within tile area 430 and restricts the type of contentallowed in the collection (other than the header information) to contentitems and metadata that are embedded in the tiles.

In some implementations, tile area 430 can include graphical element 440for adding content items to tile area 430. For example, in response toreceiving user input selecting graphical element 440, CMS client 250 canpresent a graphical user interface (e.g., similar to GUI 500 below) forselecting one or more content items to embed in the collection. Afterthe user has selected a content item (e.g., a content item from contentstorage 160, a content item from another source, etc.), client device240 can send the content item and/or content item identifier tocollections module 204. Collections module 204 can then generate acollection item identifier and a protected shared link (PSL) for thecontent item, as described above. Collections module 204 can store thecollection item identifier and the PSL in collection items 210 and sendthe PSL and collection item identifier to CMS client 250. CMS client 250can then use the PSL to obtain the corresponding content item. CMSclient 250 can use the collection item identifier to obtain thecorresponding collection item metadata. CMS client 250 can then presentthe content item and/or the collection item metadata in a tile in tilearea 430.

In some implementations, CMS client 250 can add a content item to thenew collection in response to a drag and drop input received from a userof client device 240. For example, the user can select and drag acontent item from a storage location on client device 240 and drop thecontent item in tile area 430 or on a tile representation (e.g., adashed tile placeholder) in tile area 430. In response to receiving thedrag and drop input related to the content item, client device 240 cansend the content item and/or content item identifier to collectionsmodule 204. Collections module 204 can then generate a collection itemidentifier and a protected shared link (PSL) for the content item, asdescribed above. Collections module 204 can store the collection itemidentifier and the PSL in collection items 210 and send the PSL andcollection item identifier to CMS client 250. CMS client 250 can thenuse the PSL to obtain the corresponding content item. CMS client 250 canuse the collection item identifier to obtain the correspondingcollection item metadata. CMS client 250 can then present the contentitem and/or the collection item metadata in a tile in tile area 430.

In some implementations, GUI 400 can include options area 440. Forexample, options area 440 can present graphical element 442 identifyingthe user who is currently logged into content management system 106 onclient device 240.

In some implementations, options area 440 can present graphical element442 for generating a preview of the collection. For example, acollection can have a public view and a private view. The private viewis presented to the creator and/or editor of the collection. The publicview is presented to users with whom the collection has been shared butwho do not have editing privileges with respect to the collection. Theprivate view of the collection may present additional information and/orgraphical elements that are not presented in the public view because thepublic view is intended to have a more curated look without all theextra information and tools needed to edit and manage a collection. Forexample, the public view may not include any of the editing featuresthat allow a user to add or rearrange content in the collection. Thepublic view may not include statistical information, such as the numberof times the collection has been viewed. The public view will notinclude the tile placeholders (e.g., dashed lined boxes) representingtiles that have no embedded content. When an editing or creating userselects graphical element 442 to present a preview of the collection,CMS client 250 can generate and present a public view of the collectionso that the editor can view how the collection will look when thecollection is shared with (e.g., published to) users who do not haveediting permissions for the collection.

In some implementations, options area 440 can include graphical element446 for sharing the collection with other users. For example, when CMSclient 250 receives user input selecting graphical element 446, CMSclient 250 can present a graphical user interface for selecting otherusers with whom the corresponding collection can be shared. The user ofclient device 240 can then select one or more users from the graphicaluser interface and CMS client 250 can cause collections module 204 toshare the collection with the selected users. Collections module 204can, for example, send a link to the collection to the other usersand/or add the collection to the other users' accounts managed bycontent management system 106.

FIG. 5 illustrates an example graphical user interface 500 for choosingcontent items to add to a collection. For example, GUI 500 can bepresented by CMS client 250 on a display of client device 240.

In some implementations, GUI 500 can include graphical element 502 forchoosing content items to add to a collection. For example, graphicalelement 502 can be presented in response to receiving user inputselecting graphical element 412, 414, and/or 440 of FIG. 4. Graphicalelement 502 can present folders (e.g., folders 512, 514) and/or contentitems (e.g., content items 522-530) accessible to the user accountassociated with the user who is currently logged in to contentmanagement system 106 from client device 240. The user can select acontent item folder managed by content management system 106 to causegraphical element 502 to present identifiers for content itemsassociated with the selected folder. The user can select one or more ofthe content item identifiers and then select graphical element 540 tocause CMS client 250 and/or collections module 204 to add the identifiedcontent items to the currently selected collection (e.g., a newcollection, selected collection, etc.), as described above.

FIG. 6 illustrates an example graphical user interface 600 presenting acollection having embedded content items. For example, GUI 600 can bepresented in response to the user adding content to a new collectionusing GUI 500. GUI 600 can be presented in response to the userselecting an existing collection, such as providing input to GUI 300 toselect the collection presented in collection area 316. For example, theuser can select the “Building Proposal” collection by providing inputselecting image 318 and/or title 320.

In some implementations, GUI 600 can present collection 602. Forexample, when CMS client 250 receives input selecting a collection, CMSclient 250 send a request including the collection identifier tocollections module 204. Collections module 204 can use the collectionidentifier to obtain collection header data from collections data 208.Collections module 204 can use the collection identifier to obtaincollection item identifiers from collection items 210 for the contentitem metadata (e.g., tiles) embedded in the identified collection.Collections module 204 can generate a PSL for each embedded content itemin the identified collection. Collections module 204 can send thecollection header information, collection item identifiers, and PSLs toCMS client 250 so that CMS client 250 can present collection 602 on GUI600.

As described above, collection 602 can include a header background image604 (e.g., collection image) representing collection 602. Collection 602can include an image 606 (e.g., a logo image) representing a business,product, team, or some other group or individual associated with thecollection. CMS client 250 can obtain image 604 and/or image 606 usingPSLs provided by collections manager 204. Collection 602 can includetitle 608 and introduction 610. The text for title 608 and introduction610 can be obtained from the collection header data received fromcollections module 204.

In some implementations, collection 602 can include tiles 612 and 614that include embedded content items. The embedded content items in tiles612 and 614 can be represented by a tile image (e.g., thumbnail image)that represents a portion of the embedded content item. The tile imagecan be rendered by content item module 226 when CMS client 250 requeststhe tile image from content item module 226 using the PSL for thecorresponding tile. CMS client 250 can use the collection itemidentifier associated with a tile to request metadata for the tile. Forexample, the metadata for the tile can be a combination of content itemmetadata (e.g., content item name, content item type, etc.) obtainedfrom content item module 226 and collection item metadata (e.g.,comments) obtained from collections module 204, as described above.

When a user is viewing a private, editable view of collection 602,collection 602 can include an empty tile 616 (e.g., represented bydashed line) that the user can interact with to embed additional contentinto collection 602. For example, the user can select tile 616 to causeCMS client 250 to present graphical element 502 of FIG. 5 so that theuser can select content items to add to collection 602. Alternatively,the user can drag and drop a content item onto tile 616 to cause CMSclient 250 to add the content item into collection 602. When interactingwith a private view of collection 602, the user may select and dragtiles around to change the position or arrangement of embedded contentitems in collection 602. When viewing a public, non-editable view ofcollection 602, empty tile 626 can be hidden and the user may not beable to edit collection 602.

FIG. 7 illustrates an example tile graphical user interface 700. Thefeatures described with respect to GUI 700 can be features of any orevery tile presented in a collection. For example, GUI 700 maycorrespond to tiles 612 and/or 614 of GUI 600, described above. However,when viewing a tile in a public view of a collection (e.g., collection602), the user may not be able to access any of the tile editingfeatures described with respect to GUI 700. For example, the user maynot be able to adjust the layout of a tile, replace an embedded contentitem associated with a tile, or crop the image in a tile. When viewingthe tile in a private, editable view of a collection, any or all of thedescribed editing options can be made available.

In some implementations, GUI 700 can include an image area 702. Forexample, image area 602 can present an image (e.g., tile image,thumbnail image, etc.) representing the content item embedded into thetile. The image can be obtained from content item module 226 by CMSclient 250 using the PSL provided by collection module 204.

In some implementations, GUI 700 can include area 710 for presentingmetadata and/or options for the tile. For example, area 710 can includegraphical element 712 (e.g., text) representing the name of the contentitem presented in area 702. Area 710 can include graphical element 714(e.g., text) representing a caption for the content item presented inarea 702 or representing type information for the content item if acaption has not been provided. This content item metadata (content itemname, content item type, collection item caption, etc.,) can be obtainedusing the collection item identifier provided by collections module 204,as described above.

In some implementations, area 710 can include graphical element 716 fordeleting the tile. For example, when the collection is presented in aprivate, editable view, the user can select graphical element 716 todelete the tile and corresponding embedded content item from thecollection. When the collection is presented in a public view, graphicalelement 716 can be hidden.

In some implementations, area 710 can include graphical element 718 forpresenting collection comments associated with the tile. For example, auser can select graphical element 718 to cause CMS client 250 to presenta graphical element (e.g., popup window) that presents collectioncomments associated with the tile and/or corresponding embedded contentitem, as illustrated by FIG. 10 below. Graphical element 718 can bepresented in both public and private views of the collection because anyuser may add comments to a collection and/or collection item (e.g.,tile).

In some implementations, area 710 can include graphical element 720 forinvoking a full preview of the embedded content item, as described withrespect to FIG. 8 and FIG. 9 below. For example, when graphical element720 is selected, CMS client 250 can use a PSL corresponding to thecontent item embedded in image area 702 to request a full preview of thecontent item represented in image area 702. In contrast to the tileimage presented in image area 702 that presents a portion of the contentitem (e.g., less than the entire content item), the full preview imageof the content item can be a manipulable representation of the embeddedcontent item that allows the user to view and/or navigate through theentire content item.

In some implementations, GUI 700 can include graphical element 730(e.g., a toolbar) for presenting formatting options for a tile. Forexample, when a collection is presented in a private, editable view, theuser can select a tile (e.g., touch, hover a cursor over, etc.) to causegraphical element 730 to be presented near the selected tile. The usercan then select one or more of the tile formatting options presented ongraphical element 730 to make the corresponding changes to the selectedtile.

In some implementations, graphical element 730 can include metadataorientation graphical elements 732, 734, and 736. For example, the usercan select graphical element 732, 734 and 736 to change where area 710is presented in the tile and with respect to image area 702. Forexample, when graphical element 734 is selected, CMS client 250 canpresent area 710 in a horizontal orientation below image area 702, asillustrated by image area 702 a. When graphical element 732 is selected,CMS client 250 can present area 710 in a vertical orientation to theright of image area 702, as illustrated by image area 702 b. Whengraphical element 736 is selected, CMS client 250 can present area 710in a vertical orientation similarly to image area 702 b but to the leftof image area 702.

In some implementations, graphical element 730 can include graphicalelement 738 for switching between narrow views and wide views of a tile.For example, if the tile is currently presented as a narrow tile, theuser can select graphical element 730 to cause CMS client 250 to presentthe tile in a wide view, as described above. If the tile is currentlypresented as a wide tile, the user can select graphical element 730 tocause CMS client 250 to present the tile in a narrow view, as describedabove.

In some implementations, graphical element 730 can include graphicalelement 740 for replacing a content item in the selected tile. Forexample, when a user selects graphical element 740, CMS client 250 canpresent GUI 500 of FIG. 5 so that the user can choose a new content itemto replace the content item currently embedded in the selected tile.When the user selects a new content item, CMS client 250 can communicatewith collaborations module 204 to modify the collection item entry forthe tile in collection items 210 so that the collection item entryreferences the newly selected content item.

In some implementations, graphical element 730 can include graphicalelement 742 for selecting a portion of the content item to present inthe selected tile. For example, in response to receiving a selection ofgraphical element 742, CMS client 250 can present an image cropping GUIthat allows the user to specify a portion of the corresponding contentitem to present in image area 702. After the user specifies the portionof the content item to present in image area 702, CMS client 250 cansend information identifying the location of the selected portion of theimage to collections module 104. Collections module 104 can then storethe image location information in collection items 210 so that theselected portion of the image can be presented when the content item ispresented in the future.

FIG. 8 illustrates an example graphical user interface 800 forpresenting a full preview of a content item without caption or comments.For example, GUI 800 can be presented by CMS client 250 on a display ofclient device 240 in response to a user selecting graphical element 720of FIG. 7. In some implementations, GUI 800 can include image area 802.For example, image area 802 can present a full preview of a content itemassociated with a selected tile. CMS client 250 can obtain the fullpreview of the content item from content item module 226 using a PSLassociated with the content item provided by collections module 204.Image area 802 can provide an interactive view of the content item suchthat a user can interact with image area 802 to scroll, zoom, and/orotherwise interact with the content item so that the user can viewand/or navigate through the entire content item.

In some implementations, GUI 800 can include header area 810. Forexample, area 810 can include the display name 812 and content item nameor type 814 of the content item presented in image area 802. Area 810can include the identifier 816 (e.g., name) for the currently selectedcollection. Area 810 can include graphical element 818, that whenselected, causes CMS client 250 to close GUI 800 and return to thecollection GUI 600.

In some implementations, GUI 800 can include caption area 830. Forexample, a user can provide textual input in area 830 to provide acaption descriptive of the content item presented in area 802. CMSclient 250 can send the entered caption to collections module 204.Collections module 204 can store the caption in association with thecollection item identifier for the selected tile in collection items210, as described above.

In some implementations, GUI 800 can include comments area 840. Forexample, comments area 840 can include element 842 for entering a newcomment for the corresponding content item and/or collection tile. Whenthe user enters a new comment, CMS client 250 can send the enteredcomment to collections module 204. Collections module 204 can generate acomment identifier for the comment and store the comment identifier inassociation with the collection item identifier for the selected tile incollection items 210, as described above. Collections module 204 canstore the text of the comment in association with the comment identifierin comments 212 in collections storage 206.

FIG. 9 illustrates an example graphical user interface 900 forpresenting a full preview of a content item having a caption and/orcomments. For example, GUI 900 can be presented by CMS client 250 on adisplay of client device 240 in response to a user selecting graphicalelement 720 of FIG. 7. Similarly to GUI 800, GUI 900 can include imagearea 802. For example, image area 802 can present a full preview of acontent item associated with a selected tile. CMS client 250 can obtainthe full preview of the content item from content item module 226 usinga PSL associated with the content item provided by collections module204. Image area 802 can provide an interactive view of the content itemsuch that a user can interact with image area 802 to scroll, zoom,and/or otherwise interact with the content item so that the user canview and/or navigate through the entire content item.

Similarly to GUI 800, GUI 900 can include header area 810. For example,area 810 can include the display name 812 and content item name or type814 of the content item presented in image area 802. Area 810 caninclude the identifier 816 (e.g., name) for the currently selectedcollection. Area 810 can include graphical element 818, that whenselected, causes CMS client 250 to close GUI 900 and return to thecollection GUI 600.

Similarly to GUI 800, GUI 900 can include caption area 830. For example,when CMS client 250 requests the full preview image for the content itemcorresponding to the selected tile, CMS client 250 can requestcollection metadata for the selected tile by sending the collection itemidentifier for the selected tile to collections module 204. Collectionsmodule 204 can use the collection item identifier to obtain a captionassociated with the collection item identifier from collection items210, if a caption exists. Collections module 204 can send the caption toCMS client 250 and CMS client 250 can present the caption in captionarea 830.

Similarly to GUI 800, GUI 900 can include comments area 840. Forexample, when CMS client 250 requests the full preview image for thecontent item corresponding to the selected tile, CMS client 250 canrequest collection metadata for the selected tile by sending thecollection item identifier for the selected tile to collections module204. Collections module 204 can use the collection item identifier toobtain a comment identifiers and/or comment thread identifiersassociated with the collection item identifier from collection items210, if a comments exists. Collections module 204 can obtain thecomments corresponding to the comment identifiers and/or comment threadidentifiers from comments 212. Collections module 204 can send theidentified comments (e.g., comments 904 and 906) to CMS client 250. CMSclient 250 can present the comments in comments area 840.

FIG. 10 illustrates an example graphical user interface 1000 forpresenting collection item metadata in a collection view. For example,GUI 1000 can be presented by CMS client 250 on a display of clientdevice 240. GUI 1000 can present a view (e.g., public view or privateview) of a collection similarly to GUI 600 of FIG. 6 described above.

As described with reference to FIG. 7, a tile can include image area 702and metadata area 710. Metadata area 710 can include text representing acaption associated with the content item presented in image area 702.However, in some cases, the caption may be too long (e.g., too manycharacters) to fit within metadata area 710 and must be truncated to fitwithin the available space. In some implementations, a user can causeCMS client 250 to expand metadata area 710 by providing input to (e.g.,selecting, touching, hovering over, etc.) area 1002 corresponding towhere the caption is presented in metadata area 710. In response toreceiving the user input to area 1002, CMS client 250 can expandmetadata area 710 into image area 702 (e.g., up to dashed line) so thatthe entire caption can be presented within tile 610. When the user stopsproviding input to area 1002, CMS client 250 can reduce metadata area710 to its original size.

As described above with reference to FIG. 7, a tile can includegraphical element 718 for presenting comments associated with a tile(e.g., collection item) and/or corresponding content item. For example,a user can select graphical element 718 to cause CMS client 250 torequest comments for the tile from collections module 204. For example,CMS client 250 can send the collection item identifier for the selectedtile to collections module 204. Collections module 204 can use thecollection item identifier to obtain a comment identifiers and/orcomment thread identifiers associated with the collection itemidentifier from collection items 210, if a comments exists. Collectionsmodule 204 can obtain the comments corresponding to the commentidentifiers and/or comment thread identifiers from comments 212.Collections module 204 can send the identified comments (e.g., comments1014 and 1016) to CMS client 250. When CMS client 250 receives thecomments from collections module 204, CMS client 250 can presentgraphical element 1012 (e.g., a window, popup, bubble, etc.) thatpresents the comments received from collections module 204.

FIG. 11A shows a flow diagram of an example process 1100 for creating acollection. For example, process 1100 can be performed cooperatively bycollections server 202, content item server 220, and client device 240to create a new collection.

At step 1102, client device 240 can receive user input indicating thatthe user wishes to create a new collection. For example, CMS client 250can receive a selection of graphical element 340 of FIG. 3.

At step 1104, client device 240 can send a request for a new collectionto collections server 202. For example, in response to receiving theuser input at step 1102, CMS client 250 can send a request for a newcollection to collections module 204.

At step 1106, collections server 202 can send an empty collection toclient device 250. For example, collections module 204 can generate anempty collection and send the empty collection to CMS client 250.

At step 1108, client device 240 can present the empty collection. Forexample, CMS client 250 can present the empty collection on a display ofclient device 240, as illustrated by FIG. 4. The empty collection caninclude graphical elements illustrating possible layout of tiles in thecollection. The empty collection can include graphical elements that theuser can select to add content to the empty collection.

At step 1110, client device 240 can receive user input to add content tothe empty collection. For example, the user can select one or moregraphical elements presented with the empty collection to add a headerbackground image, a logo image, and/or one or more embedded contentitems to the empty collection.

At step 1112, client device 240 can send a request to content itemserver 220 for content item identifiers representing content itemsmanaged by content item module 226. CMS client 250 can request a list ofcontent item identifiers from content item module 226 representing thecontent items for which the user has access permissions.

At step 1114, content item server 220 can generate a list of contentitem identifiers. For example, content item module 226 can generate alist of content items that the user for which the user has accesspermissions.

At step 1116, content item server 220 can send the content itemidentifiers to client device 240. For example, upon receipt of thecontent item identifiers, CMS client 250 can present a graphical userinterface (e.g., GUI 500) for choosing content items from contentstorage 160, client device 240, or some other storage location.

At step 1118, client device 240 can receive user input selecting one ormore content item identifiers from the chooser graphical user interface.For example, CMS client 250 can receive user input selecting contentitems for the header background image, a logo image, and/or one or moreembedded content items of the collection.

At step 1120, client device 240 can send the selected content itemidentifiers to collections server 202. For example, CMS client 250 cansend a message to collections module 204 indicating a selected contentitem identifier and a collections attribute (e.g., header backgroundimage, a logo image, and/or one or more embedded content items) withwhich the content item identifier is associated.

At step 1122, collections server 202 can generate a collection itemidentifier for the selected content item identifier. For example, inresponse to receiving the content item identifier, collections module204 can generate a collection item identifier for the selected contentitem identifier that can be embedded in the collection and used toreference the selected content item, as described above.

At step 1124, collections server 202 can generate a content itemidentifier to collection item identifier mapping. For example,collections module 204 can create an entry (e.g., record) in collectionitems 210 (e.g., a database table) in collections storage database 206and store content item identifier, collection item identifier,collection identifier for the new collection, and additional collectionitem attributes, as described above, in the collection items entry.

At step 1126, collections server 202 can embed the selected content itemin the collection using the collection item identifier. For example,collections module 204 can generate a new version of the collection(e.g., a web page) that includes links (e.g., URLs) that reference thecollection item identifier. The collection item identifier can be usedto generate links for the header background image, a logo image, and/orone or more embedded content items.

At step 1128, collection server 202 can send the collection with theembedded content to client device 240. For example, collections module204 can send the collection having the embedded collection itemidentifiers to CMS client 250. CMS client 250 can then present thecollection, as described below with respect to process 1200.

FIG. 11B shows a flow diagram of an example process 1150 for adding acontent item to a collection. For example, process 1150 can be performedcooperatively by collections server 202, content item server 220, andclient device 240 to create a new collection. Process 1150 can beperformed when a private, editable view of a collection (e.g., a newcollection, a selected collection, etc.) is being presented by CMSclient 250 on a display of client device 240.

At step 1152, client device 240 can receive user input identifying acontent item to add to the collection. For example, the user input canbe a drag-and-drop input where the user drags a representation of acontent item from a storage location onto the collection currentlypresented by CMS client 250.

At step 1154, client device 240 can send a request to collections server202 to add the identified content item to the currently presentedcollection. For example, the request can include the collectionidentifier for the collection and the identified content item.

At step 1156, collections server 202 can send the content item tocontent item server 220 for storage. For example, collections module 204can send the collection identifier and content item to content itemmodule 226.

At step 1158, content item server 220 can store the content item in astorage location in content storage 160 associated with the identifiedcollection. For example, content item module 226 can generate a contentitem identifier for the new content item and store the content item in afolder (e.g., shared folder) associated with the content item.

At step 1160, content item server 220 can send the content itemidentifier to collections server 202. For example, content item module226 can send the content item identifier to collections module 204.

At step 1162, collections server 202 can generate a collection itemidentifier for the selected content item identifier. For example, inresponse to receiving the content item identifier, collections module204 can generate a collection item identifier for the selected contentitem identifier that can be embedded in the collection and used toreference the selected content item, as described above.

At step 1164, collections server 202 can generate a content itemidentifier to collection item identifier mapping. For example,collections module 204 can create an entry (e.g., record) in collectionitems 210 (e.g., a database table) in collections storage database 206and store content item identifier, collection item identifier,collection identifier for the new collection, and additional collectionitem attributes, as described above, in the collection items entry.

At step 1166, collections server 202 can embed the selected content itemin the collection using the collection item identifier. For example,collections module 204 can generate a new version of the collection(e.g., a web page) that includes links (e.g., URLs) that reference thecollection item identifier. The collection item identifier can be usedto generate links for the header background image, a logo image, and/orone or more embedded content items.

At step 1168, collection server 202 can send the collection with theembedded content to client device 240. For example, collections module204 can send the collection having the embedded collection itemidentifiers to CMS client 250. CMS client 250 can then present thecollection, as described below with respect to process 1200.

FIG. 12 shows a flow diagram of an example process 1200 for presenting acollection. For example, process 12000 can be performed cooperatively bycollections server 202, content item server 220, and client device 240to present a collection on client device 240.

At step 1202, client device 240 can receive user input selecting acollection. For example, CMS client 250 can receive user input selectinga collection from the collections listed on GUI 300 of FIG. 3, asdescribed above. Alternatively, the selected collection can correspondto a new collection that has been modified to add content and where thegraphical user interface presenting the collection needs to be updated.

At step 1204, client device 240 can send the collection identifier forthe selected collection to collections server 202. For example, when theuser selects a collection, CMS client 250 can determine the collectionidentifier for the collection and send the collection identifier tocollections module 204.

At step 1206, collections server 202 can generate a collection withembedded content. For example, collections module 204 can generate thecollection by using the collection identifier to obtain collections data(e.g., attributes, images, text, collection item identifiers, etc.) fromcollections storage 206. For example, collections module 204 can use thecollection identifier to obtain header information (e.g., headerbackground image, logo image, title, introduction, etc.) fromcollections data 208. Collections module 204 can use the collectionidentifier to obtain collection item information (e.g., collection itemidentifiers, comment identifiers, etc.) from collection items 210.Collections module 204 can use the comment identifiers obtained fromcollection items 210 to obtain comments and/or comments threads for eachcollection item (e.g., tiles, embedded content items, etc.) fromcomments 212. Collections module 204 can combine all of this collectioninformation into a data structure (e.g., web page, collection object,etc.) to generate the collection.

At step 1208, collections server 202 can send the collection to clientdevice 240. For example, collections module 204 can send the collectiondata structure generated at step 1206 to CMS client 250.

At step 1210, client device 250 can request a collection item using thecollection item identifiers. For example, to obtain and present thecontent items and/or content item metadata corresponding to the headerbackground image, logo image, and tiles, CMS client 250 can send thecollection item identifiers for each of these collection attributes tocollections module 204 on collections server 202 in a request for thecorresponding content items.

At step 1212, collections server 202 can obtain a content itemidentifier corresponding to a collection item identifier from thecontent item identifier corresponding to collection item identifiermapping managed by collections module 204. For example, in response toreceiving a collection item identifier, collections module 204 canobtain the content item identifier corresponding to the receivedcollection identifier from collection items 210.

At step 1214, collections server 202 can request content item metadatafrom content item server 220. For example, collections module 204 canuse the content item identifier obtained at step 1216 to request contentitem metadata corresponding to the content item identifier from contentitem module 226 on content item server 220. The request can includeparameters specifying which content item metadata should be included orexcluded from the content item metadata returned to collections module204. For example, the parameters can specify that the content item name,the content item type, the content item size, etc., should be includedin the content item metadata. The parameters can specify that comments,edits, revisions, annotations, etc., should be excluded from the contentitem metadata. In some implementations, all available content itemmetadata can be included in the content item metadata returned tocollections module 204.

At step 1216, content item server 220 can send the content item metadatato collections server 202. For example, if collections module 204receives a content item metadata that includes all of the metadata forthe identified content item, then collections module 204 can filter thecontent item metadata to remove comments, edits, revisions, annotations,etc., in the content item metadata so that these types of metadata arenot delivered to client device 240.

At step 1218, collections server 202 can obtain collection item metadatausing the collection item identifier received at step 1210. For example,collections module 204 can obtain collection item metadata, such as acaption, comments, etc., corresponding to the collection item identifierfrom collection items 210 and comments 212 in collections storage 206.Collections module 204 can add the content item metadata to thecollections item metadata and send the collections item metadata to CMSclient 250 at step 1220 below.

At step 1219, collections server 202 can generate a protected sharedlink for obtaining a content item from content item server 220. Asdescribed above, the protected shared link (PSL) can be a URL associatedwith content item module 226 that includes an encrypted payload. Thepayload can include a URL that includes the content item identifiercorresponding to the content item, the collection identifier for therequested collection, a creation time corresponding to the time when thePSL was generated, and a time to live indicating a duration of timeduring which the PSL is valid. The payload can be encrypted using ashared secret that is shared between content item module 226 andcollections module 204.

At step 1220, collections server 202 can send the collection itemmetadata and the PSL for the content item to client device 240. Forexample, collections module 204 can send the collection item metadataand the PSL for the content item to CMS client 250.

At step 1222, client device 240 can request a collection item fromcontent item server 220 using the protected shared link. For example,CMS client 250 can send a request for a content item corresponding tothe collection item to content item module 226 on content item server220. The request can include the encrypted payload received fromcollections module 204.

At step 1224, content item server 220 can validate the protected sharedlink. For example, content item module 226 can validate the protectedshared link by attempting to decrypt the encrypted payload using theshared secret shared between collections server 202 and content itemserver 220. If content item module 226 can decrypt the encryptedpayload, then content item module 226 can determine that the encryptedpayload is a valid payload generated by collections module 204. Afterdecrypting the payload, content item module 226 can validate theprotected shared link by determining that the time when the PSL wasreceived is within the time window specified by the creation time andtime to live duration indicated in the payload. If content item module226 cannot validate the payload, then process 1200 can terminate andcontent item module 226 can return an error message to CMS client 250.If content item module 226 can validate the payload, then process 1200can continue to step 1226.

At step 1226, content item server 220 can extract a content itemidentifier from the protected shared link. For example, content itemmodule 226 can obtain the content item identifier from the decrypted PSLpayload.

At step 1228, content item server 220 can obtain the content itemcorresponding to the content item identifier. For example, content itemmodule 226 can obtain the content item corresponding to the content itemidentifier from content storage 160. In some implementations, contentitem module 226 can generate an image representing the content item. Forexample, content item module can generate a tile image (e.g., thumbnailimage) representing the content item. Content item module can generate afull preview image representing the content item.

At step 1230, content item server 220 can send the content item toclient device 240. For example, content item module 226 can send thecontent item or image of the content item to CMS client 250.

At step 1232, client device 240 can present the collection. For example,after CMS client 250 receives the content items corresponding to thecollection selected at step 1202, CMS client 250 can present thecollection on a display of client device 240. For example, CMS client250 can present the collection on a graphical user interface, asdescribed with reference to FIG. 6, FIG. 7, and FIG. 10 above.

FIG. 13 shows a flow diagram of an example process 1300 for presenting acollection item preview. For example, process 1300 can be performedcooperatively by collections server 202, content item server 220, andclient device 240 to present a collection item preview on client device240.

At step 1302, client device 240 can receive user input selecting acollection item. For example, CMS client 250 can receive user inputselecting a collection item from a collection presented by CMS client250. For example, the user can select graphical element 720 associatedwith a collection item tile, as described above with reference to FIG.7.

At step 1304, client device 240 can send the collection item identifierfor the selected collection item to collections server 202. For example,in response to receiving the input selecting graphical element 720associated with a collection item tile, CMS client 250 can send thecollection item identifier corresponding to the collection item tile tocollections module 204 in a request for a full preview of the contentitem corresponding to the collection item.

At step 1306, collections server 202 can obtain a content itemidentifier corresponding to a collection item identifier from thecontent item identifier corresponding to collection item identifiermapping managed by collections module 204. For example, in response toreceiving a collection item identifier, collections module 204 canobtain the content item identifier corresponding to the receivedcollection identifier from collection items 210.

At step 1308, collections server 202 can request content item metadatafrom content item server 220. For example, collections module 204 canuse the content item identifier obtained at step 1306 to request contentitem metadata corresponding to the content item identifier from contentitem module 226 on content item server 220. The request can includeparameters specifying which content item metadata should be included orexcluded from the content item metadata returned to collections module204. For example, the parameters can specify that the content item name,the content item type, the content item size, etc., should be includedin the content item metadata. The parameters can specify that comments,edits, revisions, annotations, etc., should be excluded from the contentitem metadata. In some implementations, all available content itemmetadata can be included in the content item metadata returned tocollections module 204.

At step 1310, content item server 220 can send the content item metadatato collections server 202. For example, if collections module 204receives a content item metadata that includes all of the metadata forthe identified content item, then collections module 204 can filter thecontent item metadata to remove comments, edits, revisions, annotations,etc., in the content item metadata so that these types of content itemmetadata are not delivered to client device 240.

At step 1312, collections server 202 can obtain collection item metadatausing the collection item identifier received at step 1304. For example,collections module 204 can obtain collection item metadata, such as acaption, comments, etc., corresponding to the collection item identifierfrom collection items 210 and comments 212 in collections storage 206.Collections module 204 can add the content item metadata to thecollections item metadata and send the collections item metadata to CMSclient 250 at step 1314 below.

At step 1313, collections server 202 can generate a protected sharedlink for obtaining a content item from content item server 220. Asdescribed above, the protected shared link (PSL) can be a URL associatedwith content item module 226 that includes an encrypted payload. Thepayload can include a URL that includes the content item identifiercorresponding to the content item, the collection identifier for therequested collection, a creation time corresponding to the time when thePSL was generated, and a time to live indicating a duration of timeduring which the PSL is valid starting at the creation time. The payloadcan be encrypted using a shared secret that is shared between contentitem module 226 and collections module 204.

At step 1314, collections server 202 can send the collection itemmetadata and the PSL for the content item to client device 240. Forexample, collections module 204 can send the collection item metadataand the PSL for the content item to CMS client 250.

At step 1316, client device 240 can request a collection item fromcontent item server 220 using the protected shared link. For example,CMS client 250 can send a request for a content item corresponding tothe collection item to content item module 226 on content item server220. The request can include the encrypted payload received fromcollections module 204.

At step 1318, content item server 220 can validate the protected sharedlink. For example, content item module 226 can validate the protectedshared link by attempting to decrypt the encrypted payload using theshared secret shared between collections server 202 and content itemserver 220. If content item module 226 can decrypt the encryptedpayload, then content item module 226 can determine that the encryptedpayload is a valid payload generated by collections module 204. Afterdecrypting the payload, content item module 226 can validate theprotected shared link by determining that the time when the PSL wasreceived is within the time window specified by the creation time andtime to live duration indicated in the payload. If content item module226 cannot validate the payload, then process 1200 can terminate andcontent item module 226 can return an error message to CMS client 250.If content item module 226 can validate the payload, then process 1300can continue to step 1320.

At step 1320, content item server 220 can extract a content itemidentifier from the protected shared link. For example, content itemmodule 226 can obtain the content item identifier from the decrypted PSLpayload.

At step 1322, content item server 220 can obtain the content itemcorresponding to the content item identifier. For example, content itemmodule 226 can obtain the content item corresponding to the content itemidentifier from content storage 160. In some implementations, contentitem module 226 can generate an image representing the content item. Forexample, content item module can generate a full preview imagerepresenting the content item.

At step 1324, content item server 220 can send the content item toclient device 240. For example, content item module 226 can send thecontent item or image of the content item to CMS client 250.

At step 1232, client device 240 can present the collection item and/orcollection item metadata. For example, after CMS client 250 receives thecontent item corresponding to the collection selected at step 1302, CMSclient 250 can present the collection item on a display of client device240. For example, CMS client 250 can present the collection item (e.g.,a full preview of the corresponding content item) on a graphical userinterface, as described with reference to FIG. 8 and FIG. 9 above.

FIG. 14 shows a flow diagram of an example process 1400 for presentingcollection item metadata. For example, process 1400 can be performedcooperatively by collections server 202, content item server 220, andclient device 240 to present a collection item metadata on client device240. For example, process 1400 can be performed to obtain collectionitem comment to be presented in graphical element 1012 of FIG. 10.

At step 1402, client device 240 can receive user input selecting acollection item. For example, CMS client 250 can receive user inputselecting a collection item from a collection presented by CMS client250. For example, the user can select graphical element 718 associatedwith a collection item tile, as described above with reference to FIG. 7and FIG. 10.

At step 1404, client device 240 can send the collection item identifierfor the selected collection item to collections server 202. For example,in response to receiving the input selecting graphical element 718associated with a collection item tile, CMS client 250 can send thecollection item identifier corresponding to the collection item tile tocollections module 204 in a request for metadata associated with thecollection item identifier.

At step 1406, collections server 202 can obtain a content itemidentifier corresponding to a collection item identifier from thecontent item identifier corresponding to collection item identifiermapping managed by collections module 204. For example, in response toreceiving a collection item identifier, collections module 204 canobtain the content item identifier corresponding to the receivedcollection identifier from collection items 210.

At step 1408, collections server 202 can request content item metadatafrom content item server 220. For example, collections module 204 canuse the content item identifier obtained at step 1406 to request contentitem metadata corresponding to the content item identifier from contentitem module 226 on content item server 220. The request can includeparameters specifying which content item metadata should be included orexcluded from the content item metadata returned to collections module204. For example, the parameters can specify that the content item name,the content item type, the content item size, etc., should be includedin the content item metadata. The parameters can specify that comments,edits, revisions, annotations, etc., should be excluded from the contentitem metadata. In some implementations, all available content itemmetadata can be included in the content item metadata returned tocollections module 204.

At step 1410, content item server 220 can send the content item metadatato collections server 202. For example, if collections module 204receives a content item metadata that includes all of the metadata forthe identified content item, then collections module 204 can filter thecontent item metadata to remove comments, edits, revisions, annotations,etc., in the content item metadata so that these types of content itemmetadata are not delivered to client device 240.

At step 1412, collections server 202 can obtain collection item metadatausing the collection item identifier received at step 1404. For example,collections module 204 can obtain collection item metadata, such as acaption, comments, etc., corresponding to the collection item identifierfrom collection items 210 and comments 212 in collections storage 206.Collections module 204 can add the content item metadata to thecollections item metadata and send the collections item metadata to CMSclient 250 at step 1414 below.

At step 1414, collections server 202 can send the collection itemmetadata for the content item to client device 240. For example,collections module 204 can send the collection item metadata for thecontent item to CMS client 250.

At step 1416, client device 240 can present the collection itemmetadata. For example, after CMS client 250 receives the content itemcorresponding to the collection selected at step 1402, CMS client 250can present the collection item metadata on a display of client device240. For example, CMS client 250 can present the collection itemmetadata (e.g., collection item comments) on graphical element 1012, asdescribed with reference to FIG. 10 above.

FIG. 15A and FIG. 15B show example possible system embodiments. The moreappropriate embodiment will be apparent to those of ordinary skill inthe art when practicing the present technology. Persons of ordinaryskill in the art will also readily appreciate that other systemembodiments are possible.

FIG. 15A illustrates a conventional system bus computing systemarchitecture 1500 wherein the components of the system are in electricalcommunication with each other using a bus 1505. Example system 1500includes a processing unit (CPU or processor) 1510 and a system bus 1505that couples various system components including the system memory 1515,such as read only memory (ROM) 1520 and random access memory (RAM) 1525,to the processor 1510. The system 1500 can include a cache of high-speedmemory connected directly with, in close proximity to, or integrated aspart of the processor 1510. The system 1500 can copy data from thememory 1515 and/or the storage device 1530 to the cache 1512 for quickaccess by the processor 1510. In this way, the cache can provide aperformance boost that avoids processor 1510 delays while waiting fordata. These and other modules can control or be configured to controlthe processor 1510 to perform various actions. Other system memory 1515may be available for use as well. The memory 1515 can include multipledifferent types of memory with different performance characteristics.The processor 1510 can include any general purpose processor and ahardware module or software module, such as module 1 1532, module 21534, and module 3 1536 stored in storage device 1530, configured tocontrol the processor 1510 as well as a special-purpose processor wheresoftware instructions are incorporated into the actual processor design.The processor 1510 may essentially be a completely self-containedcomputing system, containing multiple cores or processors, a bus, memorycontroller, cache, etc. A multi-core processor may be symmetric orasymmetric.

To enable user interaction with the computing device 1500, an inputdevice 1545 can represent any number of input mechanisms, such as amicrophone for speech, a touch-sensitive screen for gesture or graphicalinput, keyboard, mouse, motion input, speech and so forth. An outputdevice 1535 can also be one or more of a number of output mechanismsknown to those of skill in the art. In some instances, multimodalsystems can enable a user to provide multiple types of input tocommunicate with the computing device 1500. The communications interface1540 can generally govern and manage the user input and system output.There is no restriction on operating on any particular hardwarearrangement and therefore the basic features here may easily besubstituted for improved hardware or firmware arrangements as they aredeveloped.

Storage device 1530 is a non-volatile memory and can be a hard disk orother types of computer readable media which can store data that areaccessible by a computer, such as magnetic cassettes, flash memorycards, solid state memory devices, digital versatile disks, cartridges,random access memories (RAMs) 1525, read only memory (ROM) 1520, andhybrids thereof.

The storage device 1530 can include software modules 1532, 1534, 1536for controlling the processor 1510. Other hardware or software modulesare contemplated. The storage device 1530 can be connected to the systembus 1505. In one aspect, a hardware module that performs a particularfunction can include the software component stored in acomputer-readable medium in connection with the necessary hardwarecomponents, such as the processor 1510, bus 1505, display 1535, and soforth, to carry out the function.

FIG. 15B illustrates a computer system 1550 having a chipsetarchitecture that can be used in executing the described method andgenerating and displaying a graphical user interface (GUI). Computersystem 1550 is an example of computer hardware, software, and firmwarethat can be used to implement the disclosed technology. System 1550 caninclude a processor 1510, representative of any number of physicallyand/or logically distinct resources capable of executing software,firmware, and hardware configured to perform identified computations.Processor 1510 can communicate with a chipset 1560 that can controlinput to and output from processor 1510. In this example, chipset 1560outputs information to output 1565, such as a display, and can read andwrite information to storage device 1570, which can include magneticmedia, and solid state media, for example. Chipset 1560 can also readdata from and write data to RAM 1575. A bridge 1580 for interfacing witha variety of user interface components 1585 can be provided forinterfacing with chipset 1560. Such user interface components 1585 caninclude a keyboard, a microphone, touch detection and processingcircuitry, a pointing device, such as a mouse, and so on. In general,inputs to system 1550 can come from any of a variety of sources, machinegenerated and/or human generated.

Chipset 1560 can also interface with one or more communicationinterfaces 1590 that can have different physical interfaces. Suchcommunication interfaces can include interfaces for wired and wirelesslocal area networks, for broadband wireless networks, as well aspersonal area networks. Some applications of the methods for generating,displaying, and using the GUI disclosed herein can include receivingordered datasets over the physical interface or be generated by themachine itself by processor 1510 analyzing data stored in storage 1570or 1575. Further, the machine can receive inputs from a user via userinterface components 1585 and execute appropriate functions, such asbrowsing functions by interpreting these inputs using processor 1510.

It can be appreciated that example systems 1500 and 1550 can have morethan one processor 1510 or be part of a group or cluster of computingdevices networked together to provide greater processing capability.

For clarity of explanation, in some instances the present technology maybe presented as including individual functional blocks includingfunctional blocks comprising devices, device components, steps orroutines in a method embodied in software, or combinations of hardwareand software.

Any of the steps, operations, functions, or processes described hereinmay be performed or implemented by a combination of hardware andsoftware modules, alone or in combination with other devices. In anembodiment, a software module can be software that resides in memory ofa client device and/or one or more servers of a content managementsystem and perform one or more functions when a processor executes thesoftware associated with the module. The memory can be a non-transitorycomputer-readable medium.

In some embodiments the computer-readable storage devices, mediums, andmemories can include a cable or wireless signal containing a bit streamand the like. However, when mentioned, non-transitory computer-readablestorage media expressly exclude media such as energy, carrier signals,electromagnetic waves, and signals per se.

Methods according to the above-described examples can be implementedusing computer-executable instructions that are stored or otherwiseavailable from computer readable media. Such instructions can comprise,for example, instructions and data which cause or otherwise configure ageneral purpose computer, special purpose computer, or special purposeprocessing device to perform a certain function or group of functions.Portions of computer resources used can be accessible over a network.The computer executable instructions may be, for example, binaries,intermediate format instructions such as assembly language, firmware, orsource code. Examples of computer-readable media that may be used tostore instructions, information used, and/or information created duringmethods according to described examples include magnetic or opticaldisks, flash memory, USB devices provided with non-volatile memory,networked storage devices, and so on.

Devices implementing methods according to these disclosures can comprisehardware, firmware and/or software, and can take any of a variety ofform factors. Typical examples of such form factors include laptops,smart phones, small form factor personal computers, personal digitalassistants, and so on. Functionality described herein also can beembodied in peripherals or add-in cards. Such functionality can also beimplemented on a circuit board among different chips or differentprocesses executing in a single device, by way of further example.

The instructions, media for conveying such instructions, computingresources for executing them, and other structures for supporting suchcomputing resources are means for providing the functions described inthese disclosures.

Although a variety of examples and other information was used to explainaspects within the scope of the appended claims, no limitation of theclaims should be implied based on particular features or arrangements insuch examples, as one of ordinary skill would be able to use theseexamples to derive a wide variety of implementations. Further andalthough some subject matter may have been described in languagespecific to examples of structural features and/or method steps, it isto be understood that the subject matter defined in the appended claimsis not necessarily limited to these described features or acts. Forexample, such functionality can be distributed differently or performedin components other than those identified herein. Rather, the describedfeatures and steps are disclosed as examples of components of systemsand methods within the scope of the appended claims.

What is claimed is:
 1. A computer-implemented method, comprising:receiving, by a collection management system from a client device, arequest for collection item metadata associated with a collection item,the request comprising a collection item identifier; obtaining, by thecollection management system, a content item identifier corresponding tothe collection item identifier; requesting, by the collection managementsystem, content item metadata from a content management system, thecontent item metadata corresponding to the content item identifier of acontent item stored by the content management system; receiving, fromthe content management system, content item metadata corresponding tothe content item identifier; filtering, by the collection managementsystem, the content item metadata to remove a portion of the contentitem metadata comprising privileged information, comprising: removing atleast one of comments, edits, revisions, or annotations associated withthe content item; retrieving, by the collection management system,collection item metadata using the collection item identifier; adding,by the collection management system, the filtered content item metadatato the collection item metadata; and sending, by the collectionmanagement system to the client device, the collection item metadata forthe content item to be displayed to a user of the client device, withoutsending the portion of the metadata comprising privileged information.2. The computer-implemented method of claim 1, wherein requesting, bythe collection management system content item metadata from the contentmanagement system, comprises: including one or more parametersspecifying metadata to be included or excluded from the content itemmetadata returned to collection management system.
 3. Thecomputer-implemented method of claim 2, wherein the one or moreparameters specify at least one of a content item name, a content itemtype, or a content item size.
 4. The computer-implemented method ofclaim 1, further comprising: embedding the collection item metadata intothe content item collection using the collection item identifier.
 5. Thecomputer-implemented method of claim 1, wherein sending, by thecollection management system to the client device, the collection itemmetadata for the content item to be displayed to a user of the clientdevice, comprises: generating a protected shared link that comprises anencrypted payload, the encrypted payload comprising the content itemidentifier and the collection item identifier; and sending the protectedshared link and the collection item metadata to the client device. 6.The computer-implemented method of claim 5, further comprising:encrypting the payload using a shared secret that is shared betweencomponents of the collection management system.
 7. A computing system,comprising: a collections server configured to manage one or morecollections of content items; and one or more processors coupled to thecollections server, the one or more processors configured to: receive,from a client device, a request for collection item metadata associatedwith a collection item, the request comprising a collection itemidentifier; obtain a content item identifier corresponding to thecollection item identifier; request content item metadata from a contentmanagement system, the content item metadata corresponding to thecontent item identifier of a content item stored by the contentmanagement system; receive content item metadata corresponding to thecontent item identifier; filter the content item metadata to remove aportion of the content item metadata comprising privileged information,comprising: removing at least one of comments, edits, revisions, orannotations associated with the content item; retrieve collection itemmetadata using the collection item identifier; add the filtered contentitem metadata to the collection item metadata; and send to the clientdevice the collection item metadata for the content item to be displayedto a user of the client device, without sending the portion of themetadata comprising privileged information.
 8. The computing system ofclaim 7, wherein requesting content item metadata from the contentmanagement system, comprises: including one or more parametersspecifying metadata to be included or excluded from the content itemmetadata returned to collection management system.
 9. The computingsystem of claim 8, wherein the one or more parameters specify at leastone of a content item name, a content item type, or a content item size.10. The computing system of claim 7, wherein the one or more processorsare further configured to: embed the collection item metadata into thecontent item collection using the collection item identifier.
 11. Thecomputing system of claim 7, wherein sending to the client device thecollection item metadata for the content item to be displayed to a userof the client device, comprises: generating a protected shared link thatcomprises an encrypted payload, the encrypted payload comprising thecontent item identifier and the collection item identifier; and sendingthe protected shared link and the collection item metadata to the clientdevice.
 12. The computing system of claim 11, further comprising:encrypting the payload using a shared secret that is shared betweencomponents of the collection management system.
 13. A non-transitorycomputer readable medium including one or more sequences of instructionsthat, when executed by one or more processors, causes the one or moreprocessors to perform operations comprising: requesting content itemmetadata from a content management system in response to receiving arequest for collection item metadata, the content item metadatacorresponding to a content item associated with a collection itemidentifier; receiving content item metadata corresponding to the contentitem; filtering the content item metadata to remove a portion of thecontent item metadata comprising privileged information, comprising:removing at least one of comments, edits, revisions, or annotationsassociated with the content item; retrieving collection item metadatausing the collection item identifier; adding the filtered content itemmetadata to the collection item metadata; and sending the collectionitem metadata for the content item to be displayed to a user of theclient device, without sending the portion of the metadata comprisingprivileged information.
 14. The non-transitory computer readable mediumof claim 13, wherein requesting content item metadata from the contentmanagement system, comprises: including one or more parametersspecifying metadata to be included or excluded from the content itemmetadata returned to collection management system.
 15. Thenon-transitory computer readable medium of claim 14, wherein the one ormore parameters specify at least one of a content item name, a contentitem type, and a content item size.
 16. The non-transitory computerreadable medium of claim 13, wherein requesting content item metadatafrom a content management system, comprises: obtaining a content itemidentifier corresponding to the collection item identifier.
 17. Thenon-transitory computer readable medium of claim 16, wherein sending thecollection item metadata for the content item to be displayed to a userof the client device, comprises: generating a protected shared link thatcomprises an encrypted payload, the encrypted payload comprising thecontent item identifier and the collection item identifier; and sendingthe protected shared link and the collection item metadata to the clientdevice.